chore(security): add npm supply-chain guard#341
Closed
mm-yuya wants to merge 1 commit into
Closed
Conversation
mm-yuya
force-pushed
the
shiori/npm-supply-chain-guard
branch
from
c3c2885 to
dc5bbb4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
pnpm security:npm-supply-chain.Verification
node --check scripts/security/npm-supply-chain-blocklist.jsnode scripts/security/npm-supply-chain-blocklist.js-> PASS for this diffnode scripts/security/npm-supply-chain-blocklist.js --full-> ESCALATE expected because full repo contains existing@mistralai/mistralai@2.2.1namespace watch item, not a known compromised version.Notes